home *** CD-ROM | disk | FTP | other *** search
- Hidden Sculpt 3D commands
- -------------------------
-
- I found some more undocumented features of the Sculpt 3D ray tracing
- program. If some of these don't work for you, check your version. I am
- using v1.102. If you have an earlier version, you can get an update from
- Byte by Byte. The newer version is supposed to have some optimizations for
- faster rendering speeds.
-
- By clicking on the DOWN window, and then pressing CTRL-D you bring up
- a requestor that asks you for a magic number. The valid entries and
- their effects are described below.
-
- 123 Palette and Exposure lock
- Enables additional menu selections. COLOR LOCK and COLOR
- UNLOCK are added to the Observer/Mode menu, and LOCK and
- UNLOCK are added to the Observer/Exposure menu. These
- features are described in detail in the documentation for
- the latest release of MOVIE! by Eric Graham. These
- commands lock the palette and exposure of consecutive
- renderings so they may be compressed for animation.
-
- 100 Set mirror recursion depth
- Brings up a requestor that allows you to change the mirror
- recursive depth value (default is 5).
-
- 101 Set glass recursion depth
- Brings up a requestor that allows you to change the glass
- recursive depth value (default is 5).
-
- 1044 Set the debug value
- Brings up a requestor that allows you to set the debug
- value From what I saw, it seems that 0 doesn't output
- debug data, non 0 does send debug data to standard output
- (you should invoke Sculpt 3D from CLI so the output will
- go to the CLI window, or you could probably redirect it to
- a printer or file). Small numbers cause mostly timing data
- to be displayed. Large or negative numbers cause
- additional data to be displayed if the scene has mirrored
- or glass objects. It looked like the code also tested for
- debug values of 3, 4, and 5, but I couldn't see any
- difference in the output.
-
- What puzzles me is why the debug code, and the many tests against its
- value are in the release version of the program at all. Why increase
- the size of the program, load times, and execution times with runtime
- debug tests and code when it could have been conditionally compiled
- code, present during development, and absent from the release version.
- But this is a small complaint for a very good program.
-
- Steve Hatchett c/o HUBERT bbs (Nevada)
- 702-322-8877
-